pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,580,216
← previous block
next block →
recent activity
Analyzing
Block #92,580,216
12 transactions · 11 stateful · 2026-08-02 20:08:59 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,580,216
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
0x0f6795d9
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
executeBatch
· blocks 1
#8
updateTemporalNumericValuesV1
#9
0x6a6fa453
#10
setData
#11
0x59558d29
#7
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xe6611ef3…a29b
0xe52b14…7230
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x323747b7…d029
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x4a99ba46…452f
0x34b655…2a6f
2 touches
0 conflicts
0x6323c5ea…ce8a
0x34b655…2a6f
2 touches
0 conflicts
0x834437a5…ba62
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity