pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,370,702
← previous block
next block →
recent activity
Analyzing
Block #82,370,702
12 transactions · 12 stateful · 2026-06-19 19:32:48 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,370,702
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
updatePrices
#4
0xa09e9040
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x6a3599d7
#11
0xc7e3ec2c
#5
0x23afbff3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x064a3cb8…c43e
0x09475a…400f
2 touches
0 conflicts
0xd420023a…cf6a
0x09475a…400f
2 touches
0 conflicts
0x34e65d5c…838e
0xd5d960…eaee
2 touches
0 conflicts
0x541a74a9…d0c2
0xd5d960…eaee
2 touches
0 conflicts
0x88ef4191…6de8
0xd5d960…eaee
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: MarginAccount
1 conflict on slot
0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block
·
next block →
recent activity