← previous blocknext block →recent activity
Analyzing
Block #90,213,354
13 transactions · 12 stateful · 2026-07-25 13:24:26 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,213,354 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf37c63b8…6da2
0x34b655…2a6f
4 touches
1 conflict
0x0a1643e3…e20d
0x34b655…2a6f
4 touches
1 conflict
0xaaa20143…a852
0x34b655…2a6f
4 touches
1 conflict
0xee06e767…00d6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x312e4698…54c0
0x34b655…2a6f
2 touches
0 conflicts
0x34aa4690…be22
0x34b655…2a6f
2 touches
0 conflicts
0x3726966a…669d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf37c63b801…626da2
Audit this contract →
← previous block·next block →recent activity