pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,941,158
← previous block
next block →
recent activity
Analyzing
Block #83,941,158
17 transactions · 15 stateful · 2026-06-27 02:22:03 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,941,158
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xb264ae19
#2
0xab083028
#3
updatePrices
#4
0x6b8f732b
#5
0x6b8f732b
#6
0x98717539
#7
0xed82b078
#8
execFwdPositionOps
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
markGameAsLost
#12
0xe9316489
#13
setData
#14
execOrders
#15
0xc7e3ec2c
#16
0xc7e3ec2c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0xc4c04f15…738a
0x065c9d…c394
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.
← previous block
·
next block →
recent activity