← previous blocknext block →recent activity
Analyzing
Block #92,769,839
28 transactions · 27 stateful · 2026-08-03 12:03:56 UTC
Parallelism
64/100
Blocked
56%
Avg conflicts / tx
1.61
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #92,769,839 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w412w513w615w117w218w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb30f077a…1c26
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
8 touches
6 conflicts
0x976171d4…134c
0x34b655…2a6f
8 touches
6 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
8 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
21 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity