pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,429,695
← previous block
next block →
recent activity
Analyzing
Block #84,429,695
9 transactions · 7 stateful · 2026-06-29 08:36:48 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,429,695
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0xd10227eb
· blocks 1
#5
execFwdPositionOps
#6
setData
#7
0x129fa1…fbd7
#8
execOrders
#4
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x6eff5416…605d
0xea1b8e…c5ec
4 touches
1 conflict
0x3dbd9177…e936
0xea1b8e…c5ec
3 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x124be23b…2cca
0x34b655…2a6f
2 touches
0 conflicts
0x200db05e…6327
0x34b655…2a6f
2 touches
0 conflicts
0x29210375…f851
0x34b655…2a6f
2 touches
0 conflicts
0x2a9c0c09…ce85
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity