pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,724,399
← previous block
next block →
recent activity
Analyzing
Block #98,724,399
12 transactions · 11 stateful · 2026-08-24 09:39:45 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,724,399
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0x5acec890
#4
withdraw
#5
0x59558d29
#6
execute
#7
0x3f5c179b
#8
matchOrders
#9
0xed82b078
#10
approve
#11
setData
#2
0x8263f5d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb97db90…4c93
0xc8689a…ee79
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
0x7f9b5937…8eac
0x065c9d…c394
2 touches
0 conflicts
0x90a50efc…a00a
0x065c9d…c394
2 touches
0 conflicts
0x1cfd3533…fa3f
0x1c8a33…d316
2 touches
0 conflicts
0x86042c5c…ca20
0x1c8a33…d316
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:
Perpl: Settlement / Helper
1 conflict on slot
0xbb97db90cd…304c93
Audit this contract →
← previous block
·
next block →
recent activity