← previous blocknext block →recent activity
Analyzing
Block #89,566,461
14 transactions · 14 stateful · 2026-07-23 04:32:08 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,566,461 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w28w39w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4886b3df…67a3
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x6d187b4f…9f38
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x9af195fa…d000
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
15 conflicts on slot 0x4886b3dfcf…0067a3
Audit this contract →
← previous block·next block →recent activity