← previous blocknext block →recent activity
Analyzing
Block #101,502,377
14 transactions · 11 stateful · 2026-09-03 03:04:12 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,502,377 · 14 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
1w02w13w04w18w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x904e2bfb…1544
0x34b655…2a6f
4 touches
1 conflict
0xdec2aeb2…0586
0x34b655…2a6f
4 touches
1 conflict
0xd4f6a526…ad10
0x34b655…2a6f
4 touches
1 conflict
0xa735de1d…29b0
0x34b655…2a6f
4 touches
1 conflict
0x9c088939…ddd7
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0ec07cf7…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
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 0x904e2bfb75…561544
Audit this contract →
← previous block·next block →recent activity