← previous blocknext block →recent activity
Analyzing
Block #92,853,440
18 transactions · 18 stateful · 2026-08-03 19:04:40 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,853,440 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w48w59w614w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39146670…bc53
0x34b655…2a6f
10 touches
10 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x07d8b1e8…78c6
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
10 conflicts on slot 0x3914667037…e5bc53
Audit this contract →
← previous block·next block →recent activity