← previous blocknext block →recent activity
Analyzing
Block #90,819,314
28 transactions · 23 stateful · 2026-07-27 16:28:02 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,819,314 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w012w213w114w317w018w119w320w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x731f2745…9370
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xc3984dff…8118
0x065c9d…c394
4 touches
1 conflict
0x2b96d534…b6b5
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity