← previous blocknext block →recent activity
Analyzing
Block #91,770,599
19 transactions · 15 stateful · 2026-07-31 00:16:52 UTC
Parallelism
84/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,770,599 · 19 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
4w05w014w115w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd3b7baa…a256
0x34b655…2a6f
4 touches
1 conflict
0xb7fb89e5…b3c8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x41c13d6f…aec2
0x34b655…2a6f
4 touches
1 conflict
0x7b8368aa…9d5d
0x34b655…2a6f
3 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
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 0xdd3b7baa3e…72a256
Audit this contract →
← previous block·next block →recent activity