← previous blocknext block →recent activity
Analyzing
Block #89,541,016
11 transactions · 11 stateful · 2026-07-23 01:42:07 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,541,016 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1cc9519…84c1
0x34b655…2a6f
6 touches
3 conflicts
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xb678410a…0edb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1f293c1…f69c
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe819ad9d…3e2a
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
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
3 conflicts on slot 0xf1cc9519e3…fe84c1
Audit this contract →
← previous block·next block →recent activity