← previous blocknext block →recent activity
Analyzing
Block #96,025,843
15 transactions · 13 stateful · 2026-08-14 21:34:43 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,025,843 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0xd5c98027…9fd9
0x34b655…2a6f
4 touches
1 conflict
0xf5085ca5…c9b0
0x34b655…2a6f
4 touches
1 conflict
0x14d9e0d5…29cc
0x34b655…2a6f
2 touches
0 conflicts
0x3939eef2…95ad
0x34b655…2a6f
2 touches
0 conflicts
0x48b58394…2894
0x34b655…2a6f
2 touches
0 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity