pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,491,674
← previous block
next block →
recent activity
Analyzing
Block #84,491,674
27 transactions · 24 stateful · 2026-06-29 15:30:07 UTC
Parallelism
89
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,491,674
· 27 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#4
updatePrices
#5
0xccf50a51
#6
execPerpOps
#7
0xe2dc7dc3
#8
0x5a5d9a99
· blocks 1
#10
forward
#11
updateDataFeedsValuesPartial
#12
updateDataFeedsValuesPartial
#14
forward
#15
execFwdPositionOps
· blocks 1
#16
0xed82b078
· blocks 1
#17
0xed82b078
#18
0xed82b078
· blocks 1
#20
setData
#24
0x50a0b275
#25
0xc7e3ec2c
#26
0xc7e3ec2c
#2
0x0c7abd22
· blocks 2
#9
0x5a5d9a99
· blocks 1
#21
execOrders
· blocks 1
#23
0x50a0b275
#3
0x0c7abd22
#13
execFwdPositionOps
#19
0xed82b078
#22
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
8
w0
9
w1
13
w2
15
w0
16
w0
18
w0
19
w2
21
w1
22
w2
23
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x083a8763…5a7c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x2444bff8…f510
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
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:
ShMonad (shMON)
3 conflicts on slot
0x083a876309…ce5a7c
Audit this contract →
← previous block
·
next block →
recent activity