← previous blocknext block →recent activity
Analyzing
Block #91,398,492
15 transactions · 14 stateful · 2026-07-29 17:03:41 UTC
Parallelism
60/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,398,492 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2219e4e0…5923
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
8 touches
6 conflicts
0xd064a456…b881
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xd22dd5e8…83ff
0x34b655…2a6f
6 touches
3 conflicts
0xe5645bd8…a1c9
0x34b655…2a6f
6 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2219e4e088…0a5923
Audit this contract →
← previous block·next block →recent activity