← previous blocknext block →recent activity
Analyzing
Block #91,077,368
18 transactions · 17 stateful · 2026-07-28 14:07:07 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,077,368 · 18 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
2w07w08w011w113w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0xf0e8582d…e851
0x34b655…2a6f
6 touches
3 conflicts
0x107b89e4…470d
0x34b655…2a6f
4 touches
1 conflict
0x12bc23cf…d56d
0x34b655…2a6f
4 touches
1 conflict
0x1cdfd446…43f8
0x34b655…2a6f
4 touches
1 conflict
0x61852897…ee4e
0x34b655…2a6f
4 touches
1 conflict
0x6459805c…615d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity