← previous blocknext block →recent activity
Analyzing
Block #94,719,538
14 transactions · 14 stateful · 2026-08-10 07:46:48 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,719,538 · 14 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
2w03w14w25w36w48w512w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a100ac0…96d3
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe5c830a0…73b3
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x312bcb89…10b9
0x34b655…2a6f
6 touches
3 conflicts
0xa608873a…c060
0x34b655…2a6f
6 touches
3 conflicts
0x4984f7be…d515
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 0x5a100ac0d9…2396d3
Audit this contract →
← previous block·next block →recent activity