← previous blocknext block →recent activity
Analyzing
Block #91,433,731
35 transactions · 29 stateful · 2026-07-29 20:02:13 UTC
Parallelism
69/100
Blocked
59%
Avg conflicts / tx
1.29
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,433,731 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w010w011w113w214w316w418w519w220w622w523w125w526w730w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x7b80de04…86d1
0x34b655…2a6f
6 touches
3 conflicts
0x442e26a3…e968
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity