← previous blocknext block →recent activity
Analyzing
Block #94,663,059
25 transactions · 22 stateful · 2026-08-10 03:02:43 UTC
Parallelism
68/100
Blocked
36%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,663,059 · 25 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
2w03w04w06w17w28w310w011w412w513w615w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79fbfff9…c770
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc6b604e6…5152
0x34b655…2a6f
6 touches
3 conflicts
0x658d8194…6914
0x34b655…2a6f
6 touches
3 conflicts
0xaa15302b…c84e
0x34b655…2a6f
6 touches
3 conflicts
0xef3f5637…f47c
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
21 conflicts on slot 0x79fbfff901…5cc770
Audit this contract →
← previous block·next block →recent activity