← previous blocknext block →recent activity
Analyzing
Block #91,069,182
17 transactions · 17 stateful · 2026-07-28 13:25:55 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,069,182 · 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
2w03w04w17w19w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x7d435e41…3c44
0x34b655…2a6f
2 touches
0 conflicts
0x818e1296…f4d7
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 0x167de262c8…3ef61f
Audit this contract →
← previous block·next block →recent activity