← previous blocknext block →recent activity
Analyzing
Block #90,026,666
12 transactions · 10 stateful · 2026-07-24 21:40:35 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,026,666 · 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
2w03w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd40d3a10…3a44
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x76d36e11…fde2
0x34b655…2a6f
4 touches
1 conflict
0x7c7eff13…16db
0x34b655…2a6f
4 touches
1 conflict
0x8eed7e30…c1ef
0x34b655…2a6f
4 touches
1 conflict
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0xc7f6eab9…9e9f
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 0xd40d3a10f0…f33a44
Audit this contract →
← previous block·next block →recent activity