← previous blocknext block →recent activity
Analyzing
Block #96,605,985
15 transactions · 12 stateful · 2026-08-16 22:12:58 UTC
Parallelism
53/100
Blocked
58%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,605,985 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w08w39w410w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x11ba6ecb…5b99
0x34b655…2a6f
8 touches
6 conflicts
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x1e334ac0…11d3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x70e3da66…674a
0x34b655…2a6f
6 touches
3 conflicts
0x850def09…120b
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity