pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,858,972
← previous block
next block →
recent activity
Analyzing
Block #92,858,972
8 transactions · 8 stateful · 2026-08-03 19:32:32 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,858,972
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#3
0x3f5c179b
#4
0x0f6795d9
· blocks 1
#6
0x6a70ed47
#7
setData
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c955e7e…ef5e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x1d7357c6…fafe
0x34b655…2a6f
2 touches
0 conflicts
0x3260c88b…0e32
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8def
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
0x3c955e7e58…fbef5e
Audit this contract →
← previous block
·
next block →
recent activity