← previous blocknext block →recent activity
Analyzing
Block #90,853,603
14 transactions · 14 stateful · 2026-07-27 19:20:31 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,853,603 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w17w28w39w210w411w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b6efeb0…b965
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xba9f9225…2ead
0x34b655…2a6f
8 touches
6 conflicts
0xb47de4be…f8bd
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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 0x2b6efeb077…c0b965
Audit this contract →
← previous block·next block →recent activity