← previous blocknext block →recent activity
Analyzing
Block #89,545,750
19 transactions · 19 stateful · 2026-07-23 02:13:46 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,545,750 · 19 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
3w04w15w28w39w413w414w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d0a300…67ef
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9c7ecae6…f4f8
0x34b655…2a6f
6 touches
3 conflicts
0x004f611b…5f47
0x34b655…2a6f
6 touches
3 conflicts
0xd51e027e…7c31
0x34b655…2a6f
6 touches
3 conflicts
0x6e19c9a0…7d86
0x34b655…2a6f
4 touches
1 conflict
0x71892c70…660d
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
10 conflicts on slot 0x69d0a3001a…3467ef
Audit this contract →
← previous block·next block →recent activity