pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,562,874
← previous block
next block →
recent activity
Analyzing
Block #98,562,874
12 transactions · 11 stateful · 2026-08-23 19:43:07 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,562,874
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrders
#3
exactInputSingle
#4
0x59558d29
#5
0x41a8f47c
· blocks 1
#6
0x57368ddf
#8
0x6a8b4dc3
#9
setData
#10
execOrders
#11
execOrders
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12ea6b9f…260f
0x34b655…2a6f
2 touches
0 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
2 touches
0 conflicts
0x68e5627d…6f8f
0x34b655…2a6f
2 touches
0 conflicts
0x70986451…c6bd
0x34b655…2a6f
2 touches
0 conflicts
0x74a8e861…0343
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-MON/USDC
1 conflict on slot
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity