← previous blocknext block →recent activity
Analyzing
Block #91,383,816
20 transactions · 19 stateful · 2026-07-29 15:49:51 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,383,816 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w39w413w518w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x23d51e55…82c2
0x34b655…2a6f
10 touches
10 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x01a056f8…64e4
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x5cc0e9c8…3ae6
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity