← previous blocknext block →recent activity
Analyzing
Block #89,538,715
13 transactions · 11 stateful · 2026-07-23 01:26:44 UTC
Parallelism
54/100
Blocked
64%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,538,715 · 13 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
1w02w13w05w16w28w39w410w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bfc7921…ffc8
0x34b655…2a6f
8 touches
6 conflicts
0xeb403811…08ce
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x539ecb5b…871b
0x34b655…2a6f
4 touches
1 conflict
0x6fbd5ec9…7fb4
0x34b655…2a6f
4 touches
1 conflict
0x8baffe38…c8d7
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 0x6bfc7921dc…a4ffc8
Audit this contract →
← previous block·next block →recent activity