pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,045,581
← previous block
next block →
recent activity
Analyzing
Block #84,045,581
12 transactions · 11 stateful · 2026-06-27 13:57:49 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,045,581
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
· blocks 1
#3
executeBatch
#4
0xed82b078
#5
createGame
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a3fd754
#9
setData
#11
0xc7e3ec2c
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0020cef4…3ffc
0x34b655…2a6f
2 touches
0 conflicts
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x7a51f6c0…1c43
0x34b655…2a6f
2 touches
0 conflicts
0x7fdb94ce…6bd4
0x34b655…2a6f
2 touches
0 conflicts
0xafd867b7…2b2d
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
0x785889c9fb…160603
Audit this contract →
← previous block
·
next block →
recent activity