← previous blocknext block →recent activity
Analyzing
Block #101,666,048
20 transactions · 19 stateful · 2026-09-03 16:47:34 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,666,048 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w08w112w213w316w017w118w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x4089d428…b018
0x34b655…2a6f
4 touches
1 conflict
0x424634a2…68da
0x34b655…2a6f
4 touches
1 conflict
0x45e5ce50…788b
0x34b655…2a6f
4 touches
1 conflict
0x64b7d292…67c9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity