← previous blocknext block →recent activity
Analyzing
Block #92,274,331
113 transactions · 68 stateful · 2026-08-01 18:30:38 UTC
Parallelism
86/100
Blocked
76%
Avg conflicts / tx
2.42
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #92,274,331 · 113 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w120w021w023w224w225w327w428w531w832w336w138w139w248w452w567w6110w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
32 touches
120 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x10057a50…8bd0
0xd32edf…ff58
15 touches
28 conflicts
0xdb067026…9eb8
0x2b46c0…1669
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x62c3bcda…93a5
0x754704…b603
14 touches
21 conflicts
0x40970e69…da50
0x2b46c0…1669
14 touches
21 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
120 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity