← previous blocknext block →recent activity
Analyzing
Block #101,680,854
16 transactions · 15 stateful · 2026-09-03 18:02:04 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,680,854 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w18w29w310w312w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35d
0x34b655…2a6f
6 touches
3 conflicts
0x9f083426…d0f1
0x34b655…2a6f
5 touches
3 conflicts
0xb4e37808…72ab
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 0x9b4f173cee…8c94e6
Audit this contract →
← previous block·next block →recent activity