← previous blocknext block →recent activity
Analyzing
Block #94,667,979
18 transactions · 18 stateful · 2026-08-10 03:27:28 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,667,979 · 18 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
1w02w13w27w38w39w410w011w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x39ed56bf…38e2
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x39fc983b…2a6f
0x34b655…2a6f
9 touches
10 conflicts
0xa3f095f5…bd87
0x34b655…2a6f
8 touches
6 conflicts
0xef3f5637…f47c
0x34b655…2a6f
6 touches
3 conflicts
0x5e2ea201…12de
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 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity