← previous blocknext block →recent activity
Analyzing
Block #90,698,666
22 transactions · 20 stateful · 2026-07-27 06:21:00 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,698,666 · 22 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
1w02w13w24w36w08w19w211w312w214w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xa164d951…1534
0xe1c8b7…3022
8 touches
6 conflicts
0x67d846dd…358c
0x609679…7777
8 touches
6 conflicts
0x02059d37…b643
0x9f3832…4ae4
8 touches
6 conflicts
0x02059d37…b644
0x9f3832…4ae4
8 touches
6 conflicts
0x6faf6baf…150d
0x9f3832…4ae4
8 touches
6 conflicts
0x7cf5136f…ba69
0x9f3832…4ae4
8 touches
6 conflicts
0x8552457e…2abe
0xe1c8b7…3022
8 touches
6 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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity