← previous blocknext block →recent activity
Analyzing
Block #101,893,282
13 transactions · 12 stateful · 2026-09-04 11:50:39 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,893,282 · 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
1w02w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d19cd25…a3c2
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x98e2f231…ab6e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x06642587…6f1b
0x34b655…2a6f
2 touches
0 conflicts
0x23ae66b4…da29
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
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 0x0d19cd2503…42a3c2
Audit this contract →
← previous block·next block →recent activity