pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,665,795
← previous block
next block →
recent activity
Analyzing
Block #97,665,795
10 transactions · 9 stateful · 2026-08-20 15:58:09 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,665,795
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
0xab083028
#4
execOrders
#5
setData
#6
0x3f5c179b
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
0x59558d29
#2
0x1ada0a83
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc73c1716…ed9c
0x40c49f…2af0
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0xd1b29ef6…c52c
0x065c9d…c394
4 touches
1 conflict
0xb924350c…7c11
0x754704…b603
2 touches
0 conflicts
0x5a021cdd…9dd6
0xd18b7e…414b
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
0x3a921be0eb…41779c
Audit this contract →
← previous block
·
next block →
recent activity