pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,562,715
← previous block
next block →
recent activity
Analyzing
Block #98,562,715
12 transactions · 12 stateful · 2026-08-23 19:42:18 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,562,715
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
execOrders
· blocks 1
#4
exactInputSingle
#5
0x6a8b4d91
#6
0x59558d29
#8
0x3f5c179b
· blocks 1
#10
setData
#11
execOrders
#2
updatePrices
#7
0x928e4afa
#9
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xa631fd70…6b58
0x34b655…2a6f
4 touches
1 conflict
0xb4b350eb…8c96
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x928a03d9…e6af
0x34b655…2a6f
2 touches
0 conflicts
0x1d4c90ab…1ba7
0xb72e62…7777
2 touches
0 conflicts
0xd7406ee2…f854
0xb72e62…7777
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:
0xbb3f3cb7…74e046
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity