pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,850,015
← previous block
next block →
recent activity
Analyzing
Block #98,850,015
14 transactions · 12 stateful · 2026-08-24 20:12:03 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,850,015
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x928e4afa
· blocks 1
#2
0x6a8ca60b
#3
0x8263f5d9
#5
0x59558d29
#6
withdraw
#7
handleOps
#8
0x3f5c179b
#9
0x3f5c179b
#10
0x0c7abd22
#11
0x6a8ca60b
#12
setData
#13
execOrders
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c916580…77e0
0x34b655…2a6f
2 touches
0 conflicts
0x2e15e517…0228
0x34b655…2a6f
2 touches
0 conflicts
0x6b265830…5256
0x34b655…2a6f
2 touches
0 conflicts
0x70ace55b…8c81
0x34b655…2a6f
2 touches
0 conflicts
0x7ec9cda3…6ddb
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:
Perpl
1 conflict on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity