← previous blocknext block →recent activity
Analyzing
Block #90,029,825
12 transactions · 12 stateful · 2026-07-24 21:56:31 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,029,825 · 12 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x5e6a725f…3b35
0x34b655…2a6f
2 touches
0 conflicts
0x6bf457e3…9576
0x34b655…2a6f
2 touches
0 conflicts
0x89bc0d41…ae1b
0x34b655…2a6f
2 touches
0 conflicts
0x2fcd4130…b4a5
0xc8689a…ee79
2 touches
0 conflicts
0x04c8137b…e776
0xe52b14…7230
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 0xfb874a6c9f…bfcaa0
Audit this contract →
← previous block·next block →recent activity