pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,357,909
← previous block
next block →
recent activity
Analyzing
Block #93,357,909
9 transactions · 8 stateful · 2026-08-05 13:23:13 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,357,909
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#7
setData
#8
0x59558d29
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15489204…b558
0x34b655…2a6f
2 touches
0 conflicts
0x35cca7f9…79d6
0x34b655…2a6f
2 touches
0 conflicts
0x37bef14c…a6d5
0x34b655…2a6f
2 touches
0 conflicts
0x464a87bd…843a
0x34b655…2a6f
2 touches
0 conflicts
0x7af921ff…51f6
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
0x9b2d3bee9d…d68eeb
Audit this contract →
← previous block
·
next block →
recent activity