← previous blocknext block →recent activity
Analyzing
Block #100,626,904
13 transactions · 13 stateful · 2026-08-31 01:39:02 UTC
Parallelism
77/100
Blocked
15%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,626,904 · 13 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
6w07w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d116df7…de83
0x34b655…2a6f
6 touches
3 conflicts
0xc1ea6991…e00e
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x7936769e…d2d2
0x34b655…2a6f
4 touches
1 conflict
0xfa75029c…d62c
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xebe581d8…2696
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9285
0x34ae4d…3fc5
2 touches
0 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
3 conflicts on slot 0x5d116df76f…d6de83
Audit this contract →
← previous block·next block →recent activity