← previous blocknext block →recent activity
Analyzing
Block #89,546,024
18 transactions · 17 stateful · 2026-07-23 02:15:36 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,546,024 · 18 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
2w03w18w19w010w111w212w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0x2ddfdfc6…7edb
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x32f1fe90…5ee3
0x34b655…2a6f
4 touches
1 conflict
0x380539e8…67a5
0x34b655…2a6f
4 touches
1 conflict
0x3a68f769…de0b
0x34b655…2a6f
4 touches
1 conflict
0x3f687777…b076
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 0x861e5aeffa…5cd32c
Audit this contract →
← previous block·next block →recent activity