← previous blocknext block →recent activity
Analyzing
Block #90,614,228
34 transactions · 30 stateful · 2026-07-26 23:16:12 UTC
Parallelism
79/100
Blocked
63%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,614,228 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w38w19w010w111w012w115w216w017w118w220w122w023w224w125w327w228w330w431w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
10 touches
10 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0xde945aa8…1ad5
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xb18a7027…4cc6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity