← previous blocknext block →recent activity
Analyzing
Block #93,664,947
24 transactions · 20 stateful · 2026-08-06 15:06:47 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,664,947 · 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
1w02w17w110w211w313w014w415w517w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
8 touches
6 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6a46e23f…d28d
0x34b655…2a6f
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
4 touches
1 conflict
0x3b8bce46…fcfa
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity