pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,281,244
← previous block
next block →
recent activity
Analyzing
Block #86,281,244
12 transactions · 9 stateful · 2026-07-07 22:22:10 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,281,244
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x39435dac
#4
0x39435dac
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
0xed82b078
#9
0x6a4d7c89
#10
setData
#11
0x39435dac
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1278cd0d…5033
0x065c9d…c394
2 touches
0 conflicts
0x55d1039b…2c86
0x065c9d…c394
2 touches
0 conflicts
0x9d1566e1…186f
0x065c9d…c394
2 touches
0 conflicts
0xac4a37e8…b586
0x065c9d…c394
2 touches
0 conflicts
0xd775213f…690a
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.
The bottleneck
Throughput-killer:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xcc8faac238…88c766
Audit this contract →
← previous block
·
next block →
recent activity