pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,490,592
← previous block
next block →
recent activity
Analyzing
Block #84,490,592
12 transactions · 10 stateful · 2026-06-29 15:22:53 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,490,592
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
withdraw
#6
forward
#7
0xed82b078
#8
0x89324b58
#9
0x6a428e45
#10
setData
#11
0x39435dac
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x454d8940…cfe7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b67b046…7631
0x34b655…2a6f
2 touches
0 conflicts
0x134ea5b5…4601
0x34b655…2a6f
2 touches
0 conflicts
0x320ec9ea…c798
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
0xda7f9bd20d…e9e332
Audit this contract →
← previous block
·
next block →
recent activity