← previous blocknext block →recent activity
Analyzing
Block #90,220,655
10 transactions · 10 stateful · 2026-07-25 14:01:14 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,220,655 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388633a0…86cd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x21fc2471…2c10
0x34b655…2a6f
6 touches
3 conflicts
0xb25fa8e2…c9ef
0x34b655…2a6f
6 touches
3 conflicts
0x00f85ffa…56cd
0x34b655…2a6f
6 touches
3 conflicts
0x1c1e591b…d93d
0x34b655…2a6f
5 touches
3 conflicts
0x4faee57c…6ca2
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
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 0x388633a0ee…3786cd
Audit this contract →
← previous block·next block →recent activity