pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,708,548
← previous block
next block →
recent activity
Analyzing
Block #82,708,548
11 transactions · 8 stateful · 2026-06-21 09:10:03 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,708,548
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6df9e92b
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x5a5d9a99
· blocks 1
#6
0x6a37aae3
#7
0xe9316489
#8
0xa2f653…d1ef
#9
setData
#10
0x39435dac
#5
0x5a5d9a99
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
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
2 touches
0 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x11cbccc7…68ad
0x34b655…2a6f
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
0x08913286f9…0ff0df
Audit this contract →
← previous block
·
next block →
recent activity