← previous blocknext block →recent activity
Analyzing
Block #89,747,192
10 transactions · 9 stateful · 2026-07-23 22:12:31 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,747,192 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc37eb1c4…b0b1
0x34b655…2a6f
4 touches
1 conflict
0x145b9bbf…e50f
0x34b655…2a6f
2 touches
0 conflicts
0x560fe328…965b
0x34b655…2a6f
2 touches
0 conflicts
0x579d0383…186a
0x34b655…2a6f
2 touches
0 conflicts
0x6278b1b2…ba7b
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 0xe8d58d3462…c2426d
Audit this contract →
← previous block·next block →recent activity