← previous blocknext block →recent activity
Analyzing
Block #90,236,534
18 transactions · 16 stateful · 2026-07-25 15:21:19 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,236,534 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w29w311w412w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xefbe60ba…a128
0x34b655…2a6f
8 touches
6 conflicts
0xe3280296…788e
0x34b655…2a6f
7 touches
6 conflicts
0x6254804c…a03b
0x34b655…2a6f
6 touches
3 conflicts
0x70f537e8…399b
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity