pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,624,434
← previous block
next block →
recent activity
Analyzing
Block #84,624,434
9 transactions · 8 stateful · 2026-06-30 06:15:32 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,624,434
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x39435dac
· blocks 1
#5
setData
#6
0x6a435f7b
#7
0x3bb0fd…ac34
#2
0xab083028
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159b8597…48a4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0x2d7079b6…2fce
0x065c9d…c394
2 touches
0 conflicts
0x3b53f315…f397
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0xe75cebb6…6b36
0x065c9d…c394
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
0x159b8597f3…8f48a4
Audit this contract →
← previous block
·
next block →
recent activity