← previous blocknext block →recent activity
Analyzing
Block #94,796,503
13 transactions · 11 stateful · 2026-08-10 14:15:24 UTC
Parallelism
39/100
Blocked
64%
Avg conflicts / tx
1.62
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,796,503 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w48w59w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x8743e1ba…8331
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00abac72…c0c9
0x34b655…2a6f
10 touches
10 conflicts
0xdc6c3cd8…643a
0x34b655…2a6f
8 touches
6 conflicts
0xd800e635…b1d7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
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
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity