← previous blocknext block →recent activity
Analyzing
Block #90,719,359
15 transactions · 13 stateful · 2026-07-27 08:05:05 UTC
Parallelism
47/100
Blocked
62%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,719,359 · 15 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
1w02w13w25w06w37w48w59w111w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x917f99a5…7989
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xf275824d…bd82
0x34b655…2a6f
10 touches
10 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
6 touches
3 conflicts
0x78b60ad8…8468
0x34b655…2a6f
6 touches
3 conflicts
0xd84b3d53…178b
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity