pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,021,037
← previous block
next block →
recent activity
Analyzing
Block #82,021,037
9 transactions · 8 stateful · 2026-06-18 04:40:16 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,021,037
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
updateDataFeedsValuesPartial
#4
forward
#5
0xa09e9040
· blocks 1
#7
setData
#8
0x39435dac
#2
0xed82b078
#6
0xa09e9040
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3eb1a63c…0242
0x065c9d…c394
2 touches
0 conflicts
0x44c0db67…7294
0x065c9d…c394
2 touches
0 conflicts
0x57139e6c…0838
0x065c9d…c394
2 touches
0 conflicts
0xc274713c…cb14
0x065c9d…c394
2 touches
0 conflicts
0xb3572c95…9c4a
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-WETH/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity