← previous blocknext block →recent activity
Analyzing
Block #91,276,280
10 transactions · 9 stateful · 2026-07-29 06:48:37 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,276,280 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x042c9c0e…0464
0x6657d1…8ccc
2 touches
0 conflicts
0x1754d1d8…e90c
0x6657d1…8ccc
2 touches
0 conflicts
0x27a9b6cb…dbe9
0x6657d1…8ccc
2 touches
0 conflicts
0x347854e1…6a68
0x6657d1…8ccc
2 touches
0 conflicts
0x5d7487e6…f428
0x6657d1…8ccc
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity