pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,202,164
← previous block
next block →
recent activity
Analyzing
Block #83,202,164
11 transactions · 10 stateful · 2026-06-23 16:09:37 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,202,164
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
multicall
#4
0x2993270a
#5
updateDataFeedsValuesPartial
#6
exactInputSingle
#7
0x64480813
#8
setData
#9
0x39435dac
#10
0xc7e3ec2c
#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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
2 touches
0 conflicts
0x7803622f…4995
0x065c9d…c394
2 touches
0 conflicts
0xa602d0ac…1daf
0x065c9d…c394
2 touches
0 conflicts
0x1a4179d3…0f26
0x068f22…7908
2 touches
0 conflicts
0x24104c4d…3a3a
0x068f22…7908
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