pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,974,778
← previous block
next block →
recent activity
Analyzing
Block #82,974,778
14 transactions · 10 stateful · 2026-06-22 14:48:39 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,974,778
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x77813803
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
forward
#6
forward
· blocks 1
#7
forward
#9
0x39435dac
#10
0x0f6795d9
#11
0x0f6795d9
#12
0x6a394bbf
#13
setData
#8
forward
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0xbaf3aa…4970
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x29207055…dc21
0x1efe02…37d6
2 touches
0 conflicts
0x925052fa…8f5a
0x1efe02…37d6
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d619
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d61b
0xea1b8e…c5ec
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:
0xbaf3aaec…204970
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity