pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,642,684
← previous block
next block →
recent activity
Analyzing
Block #83,642,684
38 transactions · 31 stateful · 2026-06-25 17:11:05 UTC
Parallelism
84
/100
Blocked
45
%
Avg conflicts / tx
0.74
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,642,684
· 38 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0xc1274a2e
· blocks 2
#2
0x6a3d61a1
· blocks 1
#5
updatePrices
· blocks 2
#8
execOrders
· blocks 2
#10
updateDataFeedsValuesPartial
#11
0x0d03188d
#12
execPerpOps
#13
0xccf50a51
#14
0x0c7abd22
· blocks 4
#15
execPerpOps
#16
0xe2dc7dc3
#17
0x98717539
#21
0x62be7533
#23
setData
#24
updatePriceFeedsIfNecessary
#26
forward
#27
createModule
#28
execFwdPositionOps
#29
0x6df9e92b
#31
0x6a3d61a1
#32
execOrders
#36
0xc7e3ec2c
#37
0xc7e3ec2c
#3
0xab083028
· blocks 2
#6
updatePrices
· blocks 1
#9
execOrders
· blocks 3
#18
0x0c7abd22
· blocks 3
#30
0x6a3d61a1
#4
0xab083028
#7
updatePrices
#19
0x0c7abd22
· blocks 2
#22
execFwdPositionOps
· blocks 2
#20
0x0c7abd22
· blocks 1
#33
execOrders
· blocks 2
#25
0x0c7abd22
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
5
w0
6
w1
7
w2
8
w0
9
w1
14
w0
18
w1
19
w2
20
w3
22
w2
25
w4
30
w1
33
w3
34
w4
35
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f66fd15…5f58
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x1385199e…fec8
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:
FastLane: FastLaneAuctionHandler
10 conflicts on slot
0x1f66fd15eb…c75f58
Audit this contract →
← previous block
·
next block →
recent activity