← previous blocknext block →recent activity
Analyzing
Block #92,274,465
53 transactions · 33 stateful · 2026-08-01 18:31:18 UTC
Parallelism
91/100
Blocked
55%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,274,465 · 53 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w16w27w08w09w111w213w315w319w020w121w222w323w026w227w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
6 touches
3 conflicts
0xb8fccd1b…b5f2
0x2b46c0…1669
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: 0x91855e79…58ac7e
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity