← previous blocknext block →recent activity
Analyzing
Block #101,501,732
25 transactions · 21 stateful · 2026-09-03 03:00:58 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,501,732 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w113w114w215w219w220w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb9993fb6…ae62
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
4 touches
1 conflict
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity