← previous blocknext block →recent activity
Analyzing
Block #91,085,713
14 transactions · 13 stateful · 2026-07-28 14:49:08 UTC
Parallelism
86/100
Blocked
15%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,085,713 · 14 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
5w07w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x442e26a3…e968
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc4d3d66a…d7a9
0x34b655…2a6f
4 touches
1 conflict
0x2c7064fa…682d
0x34b655…2a6f
4 touches
1 conflict
0x5404749d…9408
0x34b655…2a6f
4 touches
1 conflict
0x4fb86cd0…c67c
0x34b655…2a6f
2 touches
0 conflicts
0x6ec11f62…98a6
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 0x6ca0994e1e…7002ef
Audit this contract →
← previous block·next block →recent activity