pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,761,224
← previous block
next block →
recent activity
Analyzing
Block #83,761,224
12 transactions · 9 stateful · 2026-06-26 06:21:52 UTC
Parallelism
83
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,761,224
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc1274a2e
#2
0xab083028
#3
execPerpOps
· blocks 1
#5
0x5a5d9a99
#6
0x62be7533
#7
execFwdPositionOps
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#11
execOrders
#4
execPerpOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x32329fca…2d8c
0x34b655…2a6f
4 touches
1 conflict
0xfb75de35…c59c
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x5581d709…ab77
0x2a68ba…90c5
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xf44f653f…5e1e
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
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
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity