← previous blocknext block →recent activity
Analyzing
Block #89,538,564
22 transactions · 21 stateful · 2026-07-23 01:25:44 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,538,564 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w09w110w212w313w414w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xed4cf5a9…f734
0x34b655…2a6f
8 touches
6 conflicts
0x8d5fc820…1750
0x34b655…2a6f
8 touches
6 conflicts
0x9e70dadd…810d
0x34b655…2a6f
8 touches
6 conflicts
0x167646a7…a8aa
0x34b655…2a6f
7 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity