← previous blocknext block →recent activity
Analyzing
Block #101,024,726
16 transactions · 10 stateful · 2026-09-01 11:00:41 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,024,726 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w112w213w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8ec9a76…0e02
0x34b655…2a6f
4 touches
1 conflict
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xdaaa3f96…69b7
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfca8addf…4b41
0x34b655…2a6f
4 touches
1 conflict
0xfd7f5b55…4994
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
1 conflict on slot 0xa8ec9a769c…e20e02
Audit this contract →
← previous block·next block →recent activity