← previous blocknext block →recent activity
Analyzing
Block #91,165,449
11 transactions · 11 stateful · 2026-07-28 21:30:16 UTC
Parallelism
55/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,165,449 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x2cb61687…a205
0x34b655…2a6f
6 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbc7d5199…c05f
0x34b655…2a6f
4 touches
1 conflict
0xe1af7d74…7622
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity