pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,537,487
← previous block
next block →
recent activity
Analyzing
Block #97,537,487
20 transactions · 13 stateful · 2026-08-20 05:03:44 UTC
Parallelism
90
/100
Blocked
23
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,537,487
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
#3
0x7b84f330
· blocks 1
#4
0x41a8f47c
#5
0x41a8f47c
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execOrder
#9
execPerpOps
#10
execPerpOps
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
execFwdPositionOpsV2
#14
setData
· blocks 1
#16
0x59558d29
· blocks 1
#18
execOrders
#15
setData
#17
0x59558d29
#19
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
14
w0
15
w1
16
w0
17
w1
19
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
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:
0x80c74517…647210
1 conflict on slot
0x0000000000…00004b
Audit this contract →
← previous block
·
next block →
recent activity