← previous blocknext block →recent activity
Analyzing
Block #104,159,259
9 transactions · 9 stateful · 2026-09-12 10:44:45 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,159,259 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb70218e…3367
0x34b655…2a6f
4 touches
1 conflict
0x46ee3c65…4ab8
0x34b655…2a6f
4 touches
1 conflict
0x483c2974…bee4
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x62b26c37…87d6
0x34b655…2a6f
4 touches
1 conflict
0x8088ba6a…ac5e
0x34b655…2a6f
4 touches
1 conflict
0x97420b44…a2a8
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a7
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
1 conflict on slot 0xfb70218e8d…633367
Audit this contract →
← previous block·next block →recent activity