← previous blocknext block →recent activity
Analyzing
Block #101,956,363
12 transactions · 9 stateful · 2026-09-04 17:10:39 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,956,363 · 12 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedbc2bb3…6b83
0x34b655…2a6f
4 touches
1 conflict
0xffdc4ab0…9626
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xc6d8507c…0e1d
0x34b655…2a6f
4 touches
1 conflict
0xda18212c…b8b6
0x34b655…2a6f
4 touches
1 conflict
0x0122be8d…31ca
0x34b655…2a6f
2 touches
0 conflicts
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x1b7d4588…6e24
0x34b655…2a6f
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
1 conflict on slot 0xedbc2bb35b…a16b83
Audit this contract →
← previous block·next block →recent activity