← previous blocknext block →recent activity
Analyzing
Block #90,232,519
12 transactions · 10 stateful · 2026-07-25 15:01:06 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,232,519 · 12 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
2w04w18w29w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e0a3c1a…f9fb
0x34b655…2a6f
6 touches
3 conflicts
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0xfc421e5f…71c0
0x34b655…2a6f
4 touches
1 conflict
0x00e2c296…0001
0x34b655…2a6f
4 touches
1 conflict
0x16838830…6ab2
0x34b655…2a6f
4 touches
1 conflict
0x45b57036…844b
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x0e0a3c1a06…e6f9fb
Audit this contract →
← previous block·next block →recent activity