pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,522,467
← previous block
next block →
recent activity
Analyzing
Block #82,522,467
9 transactions · 8 stateful · 2026-06-20 12:24:48 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
#82,522,467
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x5339c59f
#4
updatePrices
#5
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x32f1e744…a8b5
0x065c9d…c394
2 touches
0 conflicts
0x3e465d19…4e23
0x065c9d…c394
2 touches
0 conflicts
0x5f50f05b…2b42
0x065c9d…c394
2 touches
0 conflicts
0xa047d03a…7df7
0x065c9d…c394
2 touches
0 conflicts
0xd7da0202…65cf
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
0x5540f95607…2d69e8
Audit this contract →
← previous block
·
next block →
recent activity