← previous blocknext block →recent activity
Analyzing
Block #93,665,462
20 transactions · 20 stateful · 2026-08-06 15:09:22 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,665,462 · 20 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
5w06w17w08w110w011w212w313w015w116w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c5409a…25b7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xcc351d6d…256b
0x34b655…2a6f
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
4 touches
1 conflict
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x99c5409a28…0025b7
Audit this contract →
← previous block·next block →recent activity