← previous blocknext block →recent activity
Analyzing
Block #94,841,991
17 transactions · 17 stateful · 2026-08-10 18:04:15 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,841,991 · 17 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
1w02w13w04w15w06w07w110w211w313w414w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x41891af2…ed2a
0x34b655…2a6f
8 touches
6 conflicts
0x742436a7…c4d4
0x34b655…2a6f
8 touches
6 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
8 touches
6 conflicts
0xa074694c…7c34
0x34b655…2a6f
7 touches
6 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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity