pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,737,947
← previous block
next block →
recent activity
Analyzing
Block #82,737,947
11 transactions · 9 stateful · 2026-06-21 12:26:24 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,737,947
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x1a945f9c
#3
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
execOrders
#7
0x6a37d8e8
#8
setData
#9
withdraw
#10
0xc7e3ec2c
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
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
0x60673b5d…cde6
0x1efe02…37d6
2 touches
0 conflicts
0xcada5f50…bb00
0x1efe02…37d6
2 touches
0 conflicts
0xdffc9e7f…2100
0x1efe02…37d6
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x93f4bd7a…3a87
0x754704…b603
2 touches
0 conflicts
0xc96ef8cc…ff2e
0x754704…b603
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