pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,426,669
← previous block
next block →
recent activity
Analyzing
Block #82,426,669
9 transactions · 6 stateful · 2026-06-20 01:46:13 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,426,669
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x313001f2
#3
updateDataFeedsValuesPartial
#4
withdraw
#5
0x39abec6b
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xd40bddc1…773c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x570f5a01…28a4
0x34b655…2a6f
4 touches
1 conflict
0x64e78a02…e340
0x34b655…2a6f
4 touches
1 conflict
0x2dc68e65…3a83
0x2ab50b…5c41
2 touches
0 conflicts
0x39ba1150…19f0
0x2ab50b…5c41
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:
Perpl
1 conflict on slot
0x6f58168d48…e3ea24
Audit this contract →
← previous block
·
next block →
recent activity