pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,973,486
← previous block
next block →
recent activity
Analyzing
Block #95,973,486
8 transactions · 6 stateful · 2026-08-14 17:11:14 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,973,486
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0xcffefd2e
· blocks 1
#4
0x94defb17
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#3
0xcffefd2e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x3841818b…e1e7
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x21a4941a…e7d2
0x34b655…2a6f
2 touches
0 conflicts
0x29c1a140…099f
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d5
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d6
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
0xff19684070…f2a453
Audit this contract →
← previous block
·
next block →
recent activity