pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,556,986
← previous block
next block →
recent activity
Analyzing
Block #97,556,986
12 transactions · 11 stateful · 2026-08-20 06:42:38 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,556,986
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
0x5acec890
· blocks 1
#5
handleOps
#6
0x3f5c179b
#7
transfer
#8
setData
#9
0x59558d29
#10
execOrders
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1951ee47…540f
0x34b655…2a6f
2 touches
0 conflicts
0x1d290f8b…2ad7
0x34b655…2a6f
2 touches
0 conflicts
0x1f78d782…e1fd
0x34b655…2a6f
2 touches
0 conflicts
0x24ae63e2…f41d
0x34b655…2a6f
2 touches
0 conflicts
0x27b52496…e957
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity