← previous blocknext block →recent activity
Analyzing
Block #96,025,874
14 transactions · 13 stateful · 2026-08-14 21:34:53 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,025,874 · 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
3w04w15w28w39w410w512w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26ec135b…9718
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xe74deb99…9e5b
0x34b655…2a6f
6 touches
3 conflicts
0x0f6aef87…8137
0x34b655…2a6f
6 touches
3 conflicts
0x37d710c8…45c1
0x34b655…2a6f
6 touches
3 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
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 0x26ec135b60…939718
Audit this contract →
← previous block·next block →recent activity