pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,186,975
← previous block
next block →
recent activity
Analyzing
Block #92,186,975
11 transactions · 9 stateful · 2026-08-01 11:11:18 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,186,975
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
batchUpdate
#5
0x0f6795d9
· blocks 1
#7
forward
#8
0x6a6dd4cd
#9
setData
#10
0x59558d29
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f24a8ec…24e1
0x34b655…2a6f
4 touches
1 conflict
0x6b3c1134…cbf4
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x0a025eea…26b4
0x34b655…2a6f
2 touches
0 conflicts
0x1049eaaf…4967
0x34b655…2a6f
2 touches
0 conflicts
0x1bd6ddeb…9a19
0x34b655…2a6f
2 touches
0 conflicts
0x2aeec8e7…972a
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
0x3f24a8ec20…9d24e1
Audit this contract →
← previous block
·
next block →
recent activity