pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,768,320
← previous block
next block →
recent activity
Analyzing
Block #92,768,320
9 transactions · 7 stateful · 2026-08-03 11:56:17 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,768,320
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
#2
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xb2d4797b
#6
depositNative
#7
setData
#8
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xd1260f5d…fb81
0x34b655…2a6f
4 touches
1 conflict
0x68caa37b…c795
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0xcf6f8850…e3c2
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x0d2e1791…c1dd
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
0x81561f70ba…26fefd
Audit this contract →
← previous block
·
next block →
recent activity