← previous blocknext block →recent activity
Analyzing
Block #91,295,306
13 transactions · 11 stateful · 2026-07-29 08:24:24 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,295,306 · 13 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
2w03w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc0e9c8…3ae6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x045502c3…b241
0x34b655…2a6f
2 touches
0 conflicts
0x05414787…6b5b
0x34b655…2a6f
2 touches
0 conflicts
0x14eb2f47…8a2e
0x34b655…2a6f
2 touches
0 conflicts
0x159aac52…c583
0x34b655…2a6f
2 touches
0 conflicts
0x18e900fa…07f4
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 0x5cc0e9c8b0…1d3ae6
Audit this contract →
← previous block·next block →recent activity