← previous blocknext block →recent activity
Analyzing
Block #89,560,712
24 transactions · 22 stateful · 2026-07-23 03:53:42 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,560,712 · 24 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
1w02w110w011w112w113w217w318w119w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6c0349d…05b0
0x34b655…2a6f
6 touches
3 conflicts
0x2b98be55…d0df
0x34b655…2a6f
4 touches
1 conflict
0x2cd98078…527c
0x34b655…2a6f
4 touches
1 conflict
0x4a119a69…cb56
0x34b655…2a6f
4 touches
1 conflict
0x4cfcdbfb…f9b6
0x34b655…2a6f
4 touches
1 conflict
0x8047e9b2…9bb8
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity