← previous blocknext block →recent activity
Analyzing
Block #90,500,267
10 transactions · 10 stateful · 2026-07-26 13:42:57 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,500,267 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd22ea5b1…7dcb
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0308
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0309
0x34b655…2a6f
4 touches
1 conflict
0xf093e256…6c4d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1528f63c…d1c5
0x34b655…2a6f
4 touches
1 conflict
0x1821c155…70ef
0x34b655…2a6f
4 touches
1 conflict
0x463e8557…882c
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
1 conflict on slot 0xd22ea5b1a4…c87dcb
Audit this contract →
← previous block·next block →recent activity