← previous blocknext block →recent activity
Analyzing
Block #99,256,066
17 transactions · 17 stateful · 2026-08-26 06:21:40 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,256,066 · 17 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
1w03w07w111w113w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40d6d1e9…131e
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1ada3764…d906
0x34b655…2a6f
4 touches
1 conflict
0x556beb43…e627
0x34b655…2a6f
4 touches
1 conflict
0x5cd3006f…3d44
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
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
3 conflicts on slot 0x40d6d1e99d…4f131e
Audit this contract →
← previous block·next block →recent activity