← previous blocknext block →recent activity
Analyzing
Block #92,346,758
64 transactions · 54 stateful · 2026-08-02 00:34:53 UTC
Parallelism
69/100
Blocked
80%
Avg conflicts / tx
2.61
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #92,346,758 · 64 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w08w111w212w313w414w117w418w519w626w527w328w629w430w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
10 touches
10 conflicts
0xb746c3b8…98d9
0xd32edf…ff58
9 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 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: 0x91855e79…58ac7e
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity