← previous blocknext block →recent activity
Analyzing
Block #101,663,357
84 transactions · 83 stateful · 2026-09-03 16:34:02 UTC
Parallelism
96/100
Blocked
2%
Avg conflicts / tx
0.06
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,663,357 · 84 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
1w081w082w183w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x926971b8…7703
0x34b655…2a6f
4 touches
1 conflict
0x970667dd…fb66
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xe09e568f…0535
0x34b655…2a6f
4 touches
1 conflict
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0x7451c5f5…a07a
0x34b655…2a6f
3 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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity