← previous blocknext block →recent activity
Analyzing
Block #92,515,755
11 transactions · 10 stateful · 2026-08-02 14:44:48 UTC
Parallelism
28/100
Blocked
70%
Avg conflicts / tx
2.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,515,755 · 11 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
1w02w13w24w35w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdf616f1…d568
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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 0xbdf616f1b7…dcd568
Audit this contract →
← previous block·next block →recent activity