← previous blocknext block →recent activity
Analyzing
Block #92,274,334
91 transactions · 64 stateful · 2026-08-01 18:30:39 UTC
Parallelism
77/100
Blocked
70%
Avg conflicts / tx
3.74
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #92,274,334 · 91 txs across 21 waves · depth 21
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
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w421w528w629w731w832w934w1035w1149w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
42 touches
210 conflicts
0xa734c404…1247
0xd32edf…ff58
25 touches
78 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
18 touches
36 conflicts
0x40970e69…da50
0x2b46c0…1669
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0xee3b1b53…77dd
0xa6afd3…d132
18 touches
36 conflicts
0x5778d110…d2e6
0xc8689a…ee79
18 touches
36 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
210 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity