← previous blocknext block →recent activity
Analyzing
Block #93,182,711
30 transactions · 29 stateful · 2026-08-04 22:42:22 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,182,711 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w110w011w112w313w414w515w116w218w319w421w323w525w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bc53a3…c2fe
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xa7f92fce…e881
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 0xd8bc53a346…42c2fe
Audit this contract →
← previous block·next block →recent activity