pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,805,081
← previous block
next block →
recent activity
Analyzing
Block #82,805,081
9 transactions · 7 stateful · 2026-06-21 19:54:26 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,805,081
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#5
setData
#6
0x0f6795d9
#7
0x0f6795d9
#8
0x34653439
#4
0x23afbff3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f3f308b…b4b6
0x065c9d…c394
4 touches
1 conflict
0xd5929769…43c9
0x065c9d…c394
3 touches
1 conflict
0x75f1c551…a423
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x91a49a97…3cd1
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
0x3f3f308be1…7db4b6
Audit this contract →
← previous block
·
next block →
recent activity