pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,018,623
← previous block
next block →
recent activity
Analyzing
Block #82,018,623
12 transactions · 10 stateful · 2026-06-18 04:24:10 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,018,623
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5a5d9a99
#5
addBuyOrder
#6
execute
· blocks 2
#9
0xd4efb4…16a1
#10
setData
#11
execOrders
#7
execute
· blocks 1
#8
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x797464db…e15a
0x788571…8888
6 touches
3 conflicts
0xa743c8dd…ebf2
0x788571…8888
6 touches
3 conflicts
0x771a3650…01cd
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0001
0x24b18e…3301
6 touches
3 conflicts
0x00000000…0000
0x24b18e…3301
6 touches
3 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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:
0x788571e0…f48888
3 conflicts on slot
0x797464dbf4…70e15a
Audit this contract →
← previous block
·
next block →
recent activity