← previous blocknext block →recent activity
Analyzing
Block #90,330,264
7 transactions · 7 stateful · 2026-07-25 23:16:06 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,330,264 · 7 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0xa5420e1f…3788
0x34b655…2a6f
4 touches
1 conflict
0x4de96d1d…b043
0x34b655…2a6f
2 touches
0 conflicts
0x6e90b9b1…dca8
0x34b655…2a6f
2 touches
0 conflicts
0x7abc2f28…1a11
0x34b655…2a6f
2 touches
0 conflicts
0x991e2e20…94a6
0x34b655…2a6f
2 touches
0 conflicts
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity