← previous blocknext block →recent activity
Analyzing
Block #91,110,269
22 transactions · 20 stateful · 2026-07-28 16:52:42 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,110,269 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w110w011w113w118w219w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0d4839e4…4575
0x34b655…2a6f
4 touches
1 conflict
0x149de518…dcf1
0x34b655…2a6f
4 touches
1 conflict
0x1bf82572…4498
0x34b655…2a6f
4 touches
1 conflict
0x1c7801b6…1986
0x34b655…2a6f
4 touches
1 conflict
0x277ad626…7cd8
0x34b655…2a6f
4 touches
1 conflict
0x33121676…b6b8
0x34b655…2a6f
4 touches
1 conflict
0x37fc813f…859e
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
1 conflict on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity