← previous blocknext block →recent activity
Analyzing
Block #91,041,308
13 transactions · 12 stateful · 2026-07-28 11:05:41 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,041,308 · 13 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
2w03w15w26w38w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e704f63…38e8
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xcfcb676f…2dea
0x34b655…2a6f
4 touches
1 conflict
0xf30b9357…2e1e
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x102cd36e…9871
0x34b655…2a6f
4 touches
1 conflict
0x11435133…4bf8
0x34b655…2a6f
4 touches
1 conflict
0x2a1544ad…9f70
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 0x4e704f6308…6a38e8
Audit this contract →
← previous block·next block →recent activity