← previous blocknext block →recent activity
Analyzing
Block #106,381,579
29 transactions · 25 stateful · 2026-09-20 05:37:28 UTC
Parallelism
86/100
Blocked
52%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,381,579 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w06w17w18w010w011w115w116w118w221w222w123w124w225w327w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa81f368…5ed8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
6 touches
3 conflicts
0x02fa927d…6468
0x34b655…2a6f
6 touches
3 conflicts
0x66f2c527…c256
0x34b655…2a6f
4 touches
1 conflict
0x89eaf36a…4e48
0x34b655…2a6f
4 touches
1 conflict
0x8bdb417a…f069
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xfa81f36867…bc5ed8
Audit this contract →
← previous block·next block →recent activity