← previous blocknext block →recent activity
Analyzing
Block #89,861,612
19 transactions · 16 stateful · 2026-07-24 07:49:46 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,861,612 · 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
7w08w09w110w212w313w414w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
12 touches
15 conflicts
0x92339d95…0800
0xb1c8ea…8888
10 touches
10 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0a7bbfd8…ebde
0x34b655…2a6f
2 touches
0 conflicts
0x0e3b59e9…d9d0
0x34b655…2a6f
2 touches
0 conflicts
0x149de518…dcf1
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 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: 0x0000a8fd…758888
15 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity