pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,399,977
← previous block
next block →
recent activity
Analyzing
Block #83,399,977
12 transactions · 12 stateful · 2026-06-24 14:11:07 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,399,977
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 2
#3
forward
#4
batchCancelOrders
#7
updateDataFeedsValuesPartial
#8
forward
#9
execFwdPositionOps
#10
0x6a3be5f3
#11
setData
#5
0x98717539
· blocks 1
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0x65bb8d8c…8bb0
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0x80ca292a…e624
0x34b655…2a6f
4 touches
1 conflict
0xec7b070f…db9a
0x34b655…2a6f
4 touches
1 conflict
0x9cf5ac50…1be9
0xa6afd3…d132
2 touches
0 conflicts
0xbaff104b…3edb
0xa6afd3…d132
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
3 conflicts on slot
0xe99d8e683a…2ea16e
Audit this contract →
← previous block
·
next block →
recent activity