pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,039,307
← previous block
next block →
recent activity
Analyzing
Block #84,039,307
9 transactions · 6 stateful · 2026-06-27 13:16:00 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,039,307
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#6
0x0f6795d9
#7
setData
#8
0x39435dac
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe560375e…4626
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x044b03fb…cbae
0x34b655…2a6f
2 touches
0 conflicts
0x0855003b…ad3e
0x34b655…2a6f
2 touches
0 conflicts
0x2c4b1b8e…8392
0x34b655…2a6f
2 touches
0 conflicts
0x394b9b59…9362
0x34b655…2a6f
2 touches
0 conflicts
0x3eef5e65…6eb0
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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
0xe560375e1e…614626
Audit this contract →
← previous block
·
next block →
recent activity