← previous blocknext block →recent activity
Analyzing
Block #90,530,676
13 transactions · 13 stateful · 2026-07-26 16:15:54 UTC
Parallelism
62/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,530,676 · 13 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
3w04w18w210w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef7cdebf…b33b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd708bac6…2e5d
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x2e4e7336…e906
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: Perpl
1 conflict on slot 0xef7cdebfc1…cab33b
Audit this contract →
← previous block·next block →recent activity