pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,355,525
← previous block
next block →
recent activity
Analyzing
Block #84,355,525
11 transactions · 11 stateful · 2026-06-29 00:22:28 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,355,525
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x5a5d9a99
#4
0x0f6795d9
#5
forward
#6
0xed82b078
· blocks 1
#8
0x0f6795d9
#9
setData
#10
0xc7e3ec2c
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1222e42d…7dc8
0x34b655…2a6f
2 touches
0 conflicts
0x1c763cd1…4d3a
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x3958d3a3…425b
0x34b655…2a6f
2 touches
0 conflicts
0x40fd8994…f83e
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:
0x40c49f17…d22af0
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity