pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,914,614
← previous block
next block →
recent activity
Analyzing
Block #98,914,614
10 transactions · 8 stateful · 2026-08-25 01:37:03 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,914,614
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x41a8f47c
#3
0x4efebe…9d3a
#4
0x3f5c179b
#5
execFwdPositionOpsV2
#6
forward
#7
execFwdPositionOpsV2
#9
execOrders
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9615cf6…c97f
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0a5e7dd7…321c
0x065c9d…c394
2 touches
0 conflicts
0x6c6ed71a…c2d8
0x065c9d…c394
2 touches
0 conflicts
0x8e66da19…66b6
0x065c9d…c394
2 touches
0 conflicts
0xd8a20b36…a433
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot
0xe9615cf664…a1c97f
Audit this contract →
← previous block
·
next block →
recent activity