pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,702,593
← previous block
next block →
recent activity
Analyzing
Block #82,702,593
8 transactions · 7 stateful · 2026-06-21 08:30:18 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,702,593
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x39435dac
· blocks 2
#7
0xc7e3ec2c
#5
0x39435dac
· blocks 1
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x170e4e4c…2b90
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfd5ef2cf…02ae
0x34b655…2a6f
4 touches
1 conflict
0x3133f94b…f76b
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
0x8922b27c…9168
0x34b655…2a6f
4 touches
1 conflict
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:
Perpl
3 conflicts on slot
0x170e4e4c7c…012b90
Audit this contract →
← previous block
·
next block →
recent activity