← previous blocknext block →recent activity
Analyzing
Block #90,559,080
20 transactions · 19 stateful · 2026-07-26 18:38:46 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,559,080 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w38w29w310w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1282d637…5ff4
0x34b655…2a6f
8 touches
6 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2ee5c07b…7eb9
0x34b655…2a6f
4 touches
1 conflict
0x55a5e3ce…a2c7
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
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
6 conflicts on slot 0x1282d63734…045ff4
Audit this contract →
← previous block·next block →recent activity