pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,599,401
← previous block
next block →
recent activity
Analyzing
Block #84,599,401
10 transactions · 9 stateful · 2026-06-30 03:28:50 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,599,401
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
· blocks 1
#4
execFwdPositionOps
#5
executeBatch
#6
execFwdPositionOps
#7
0x6a43386a
#8
withdraw
#9
setData
#3
execOrders
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
0xf1e0175c…5649
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x1ca5aec6…c1e1
0x34b655…2a6f
4 touches
1 conflict
0x211cb5d5…c111
0x34b655…2a6f
4 touches
1 conflict
0x234ddf93…cda5
0x34b655…2a6f
4 touches
1 conflict
0x2e996fb7…08f6
0x34b655…2a6f
4 touches
1 conflict
0x3f75fb9e…0d2e
0x34b655…2a6f
4 touches
1 conflict
0x40b5f387…a164
0x34b655…2a6f
4 touches
1 conflict
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
0xf1e0175c33…8c5649
Audit this contract →
← previous block
·
next block →
recent activity