← previous blocknext block →recent activity
Analyzing
Block #91,408,213
13 transactions · 7 stateful · 2026-07-29 17:52:51 UTC
Parallelism
85/100
Blocked
14%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,408,213 · 13 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x010b6bfe…4581
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x07fd7215…d50e
0x34b655…2a6f
2 touches
0 conflicts
0x0b6605df…08f8
0x34b655…2a6f
2 touches
0 conflicts
0x0b7094d9…4373
0x34b655…2a6f
2 touches
0 conflicts
0x1f02e5b0…3439
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 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity