pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,606,389
← previous block
next block →
recent activity
Analyzing
Block #98,606,389
14 transactions · 11 stateful · 2026-08-23 23:30:05 UTC
Parallelism
79
/100
Blocked
18
%
Avg conflicts / tx
0.21
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,606,389
· 14 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa9b28aa6
· blocks 2
#3
0x32d01e04
#4
execOrders
#5
exactInputSingle
#6
0x59558d29
#7
0xe3a3c9cc
#8
0x62be7533
#9
forward
#11
0xed82b078
#12
setData
#13
execOrders
#2
0xab083028
· blocks 1
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1d76b8ca…c509
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity