← previous blocknext block →recent activity
Analyzing
Block #89,699,366
16 transactions · 16 stateful · 2026-07-23 18:11:04 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,699,366 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w38w49w510w612w215w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff6dd4d…e44d
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x65d63aa3…d144
0x34b655…2a6f
4 touches
1 conflict
0x71a3fd70…4a5b
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0x9ff6dd4da0…21e44d
Audit this contract →
← previous block·next block →recent activity