pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,287,640
← previous block
next block →
recent activity
Analyzing
Block #95,287,640
12 transactions · 9 stateful · 2026-08-12 07:35:34 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,287,640
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x693c2be6
#2
execOrders
#3
0x000000b2
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0x6a7c22be
#8
setData
#9
0x59558d29
#10
execOrders
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x961096d6…2a46
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x43fd3667…094b
0x34b655…2a6f
2 touches
0 conflicts
0x444eb03f…15d7
0x34b655…2a6f
2 touches
0 conflicts
0x49c03b0b…e048
0x34b655…2a6f
2 touches
0 conflicts
0x626bd7f0…ecf4
0x34b655…2a6f
2 touches
0 conflicts
0x66d5e476…8a1f
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
0x961096d610…5f2a46
Audit this contract →
← previous block
·
next block →
recent activity