← previous blocknext block →recent activity
Analyzing
Block #100,421,004
19 transactions · 17 stateful · 2026-08-30 08:23:06 UTC
Parallelism
68/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,421,004 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w312w013w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xe226a0be…c046
0x34b655…2a6f
6 touches
3 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
6 touches
3 conflicts
0x4b5f2081…f3c5
0x34b655…2a6f
6 touches
3 conflicts
0x5cd3006f…3d44
0x34b655…2a6f
6 touches
3 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity