← previous blocknext block →recent activity
Analyzing
Block #104,199,167
14 transactions · 11 stateful · 2026-09-12 14:07:13 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,199,167 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa47b7766…ee6e
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xde95b18d…3751
0x34b655…2a6f
4 touches
1 conflict
0xe2c4da1c…0e41
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x640c4fb2…044a
0x34b655…2a6f
4 touches
1 conflict
0x1f459632…a5d9
0x34b655…2a6f
4 touches
1 conflict
0xa64c11c3…70b2
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 0xa47b776601…7cee6e
Audit this contract →
← previous block·next block →recent activity