← previous blocknext block →recent activity
Analyzing
Block #89,742,192
19 transactions · 17 stateful · 2026-07-23 21:47:15 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,742,192 · 19 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
1w03w04w16w18w29w210w011w112w213w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0xe8d58d34…426d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity