← previous blocknext block →recent activity
Analyzing
Block #92,422,567
23 transactions · 16 stateful · 2026-08-02 06:56:06 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,422,567 · 23 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
1w06w112w015w116w217w318w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x07d3936c…ca02
0x34b655…2a6f
4 touches
1 conflict
0x2a1544ad…9f70
0x34b655…2a6f
4 touches
1 conflict
0x2cf53cbd…71da
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity