← previous blocknext block →recent activity
Analyzing
Block #89,548,847
10 transactions · 10 stateful · 2026-07-23 02:34:29 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,548,847 · 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
2w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e19c9a0…7d86
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0a7bbfd8…ebde
0x34b655…2a6f
2 touches
0 conflicts
0x0cfab713…3f7e
0x34b655…2a6f
2 touches
0 conflicts
0x1903eb8c…d126
0x34b655…2a6f
2 touches
0 conflicts
0x1953dd4a…340b
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 0x6e19c9a020…2f7d86
Audit this contract →
← previous block·next block →recent activity