pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,975,564
← previous block
next block →
recent activity
Analyzing
Block #82,975,564
13 transactions · 10 stateful · 2026-06-22 14:53:54 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,975,564
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x6a394cfa
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
forward
· blocks 1
#6
forward
#7
forward
#9
0x0f6795d9
#10
0x0f6795d9
#11
setData
#12
0x39435dac
#8
forward
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x5658ec…1730
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x08913286…f0df
0x34b655…2a6f
2 touches
0 conflicts
0x459573ed…fbbe
0x34b655…2a6f
2 touches
0 conflicts
0x4ea3b512…07e9
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:
0x5658ec04…1e1730
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity