pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,268,226
← previous block
next block →
recent activity
Analyzing
Block #95,268,226
11 transactions · 11 stateful · 2026-08-12 05:57:44 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,268,226
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
#3
0x0f6795d9
#4
placeAndExecuteMarketBuy
· blocks 1
#6
forward
#7
0x6a7c0bd0
#8
transfer
#9
setData
#10
0x59558d29
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x015694af…da11
0x40c49f…2af0
3 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x33b5035a…d1c6
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2593
0x34b655…2a6f
2 touches
0 conflicts
0x44a35e35…6dcf
0x34b655…2a6f
2 touches
0 conflicts
0x51134e2a…e079
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x002fed350f…7379fa
Audit this contract →
← previous block
·
next block →
recent activity