← previous blocknext block →recent activity
Analyzing
Block #91,956,017
21 transactions · 21 stateful · 2026-07-31 15:49:43 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,956,017 · 21 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
2w03w14w26w38w410w011w112w515w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9365e097…ff56
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x539ac47f…eb6f
0x34b655…2a6f
6 touches
3 conflicts
0x5d917b1d…9a71
0x34b655…2a6f
6 touches
3 conflicts
0x8472d5df…1e23
0x34b655…2a6f
6 touches
3 conflicts
0xfcbd9ef4…3e34
0x34b655…2a6f
6 touches
3 conflicts
0x26444b91…765e
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity