← previous blocknext block →recent activity
Analyzing
Block #90,992,622
18 transactions · 17 stateful · 2026-07-28 07:00:02 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,992,622 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w39w010w411w514w415w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aae14e2…64f1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4e089204…52fc
0x34b655…2a6f
4 touches
1 conflict
0x571aa8b4…35fa
0x34b655…2a6f
4 touches
1 conflict
0x6aac0528…d69d
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 0x0aae14e23f…1a64f1
Audit this contract →
← previous block·next block →recent activity