← previous blocknext block →recent activity
Analyzing
Block #92,548,966
24 transactions · 22 stateful · 2026-08-02 17:31:49 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,548,966 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w27w39w010w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xe2142951…6af0
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
10 touches
10 conflicts
0x80a49a52…b8af
0x34b655…2a6f
6 touches
4 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0x7fe8b5d8…3e49
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity