← previous blocknext block →recent activity
Analyzing
Block #90,068,293
11 transactions · 10 stateful · 2026-07-25 01:10:57 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,068,293 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecc655f1…34c8
0x34b655…2a6f
6 touches
3 conflicts
0x0cc65720…396c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x22c6ecc6…c70d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
3 conflicts on slot 0xecc655f12f…e934c8
Audit this contract →
← previous block·next block →recent activity