← previous blocknext block →recent activity
Analyzing
Block #90,865,873
18 transactions · 18 stateful · 2026-07-27 20:22:18 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,865,873 · 18 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
3w04w15w26w37w48w59w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x537bdd2d…a5e1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x0c233c18…37bb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
6 touches
3 conflicts
0xdf2011db…90e4
0x34b655…2a6f
6 touches
3 conflicts
0x09b717c6…dbac
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
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 0x537bdd2da6…86a5e1
Audit this contract →
← previous block·next block →recent activity