pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,724,982
← previous block
next block →
recent activity
Analyzing
Block #82,724,982
10 transactions · 10 stateful · 2026-06-21 10:59:42 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,724,982
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xab083028
#3
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x6a37c496
#7
setData
#8
0x39435dac
#9
0xc7e3ec2c
#4
0x40e79b1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2d35363c…104d
0x065c9d…c394
2 touches
0 conflicts
0x4ae7338e…550d
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x58288509…f330
0x065c9d…c394
2 touches
0 conflicts
0x930edb63…6ad5
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity