← previous blocknext block →recent activity
Analyzing
Block #90,385,655
16 transactions · 15 stateful · 2026-07-26 04:00:05 UTC
Parallelism
63/100
Blocked
60%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,385,655 · 16 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
1w02w13w25w06w17w28w39w210w414w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73d5bd35…5799
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0x73d5bd351e…d05799
Audit this contract →
← previous block·next block →recent activity