← previous blocknext block →recent activity
Analyzing
Block #92,482,408
24 transactions · 21 stateful · 2026-08-02 11:57:06 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,482,408 · 24 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
1w02w13w07w08w19w210w111w212w213w215w316w417w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe61d2149…e827
0x34b655…2a6f
6 touches
3 conflicts
0xee3b1b53…77dd
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x4e7eb462…b2ae
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity