← previous blocknext block →recent activity
Analyzing
Block #93,359,595
66 transactions · 60 stateful · 2026-08-05 13:31:42 UTC
Parallelism
73/100
Blocked
75%
Avg conflicts / tx
3.14
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #93,359,595 · 66 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w110w111w212w313w414w515w616w517w619w749w555w756w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x84ecf229…08e9
0xd32edf…ff58
15 touches
28 conflicts
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 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