← previous blocknext block →recent activity
Analyzing
Block #92,858,296
48 transactions · 45 stateful · 2026-08-03 19:29:07 UTC
Parallelism
71/100
Blocked
78%
Avg conflicts / tx
2.67
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #92,858,296 · 48 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w19w010w111w215w216w317w320w121w325w428w230w531w632w734w637w841w242w1143w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d94334a…8a96
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
12 touches
15 conflicts
0xd30f9e74…d404
0x34b655…2a6f
10 touches
10 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
10 touches
10 conflicts
0x840d3ab7…c8c4
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: Perpl
36 conflicts on slot 0x4d94334a63…6a8a96
Audit this contract →
← previous block·next block →recent activity