← previous blocknext block →recent activity
Analyzing
Block #92,578,843
18 transactions · 17 stateful · 2026-08-02 20:02:05 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,578,843 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w29w010w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xce06a0f7…efef
0x34b655…2a6f
11 touches
15 conflicts
0x513b12c7…47cd
0x34b655…2a6f
7 touches
6 conflicts
0xeed7ab7a…6d1f
0x34b655…2a6f
7 touches
6 conflicts
0x34806b11…bdf5
0x34b655…2a6f
7 touches
6 conflicts
0x482471ad…122f
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity