pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,448,748
← previous block
next block →
recent activity
Analyzing
Block #98,448,748
9 transactions · 9 stateful · 2026-08-23 09:56:42 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,448,748
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x6ad2e98b
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
setData
#8
execOrders
#2
0xab083028
· blocks 1
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
2 touches
0 conflicts
0x0be747d5…22e1
0x34b655…2a6f
2 touches
0 conflicts
0x19c8761d…3061
0x34b655…2a6f
2 touches
0 conflicts
0x2351a489…2aa1
0x34b655…2a6f
2 touches
0 conflicts
0x2aafbaf5…0e34
0x34b655…2a6f
2 touches
0 conflicts
0x7d8dcedc…d3dd
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: Market-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity