pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,495,099
← previous block
next block →
recent activity
Analyzing
Block #83,495,099
37 transactions · 29 stateful · 2026-06-25 00:46:10 UTC
Parallelism
84
/100
Blocked
59
%
Avg conflicts / tx
1.08
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,495,099
· 37 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x0c7abd22
· blocks 9
#4
0x6a3c7ac9
#5
execute
#6
0x6a3c7ac9
#7
0xcf7468f4
#9
0x6a3c7ac9
#12
exactOutputSingle
#13
batchUpdate
· blocks 1
#14
batchUpdate
#18
updateDataFeedsValuesPartial
#19
updateDataFeedsValuesPartial
#20
execPerpOps
#21
0x6a3c7ac9
#22
0x6b8f732b
#23
0x98717539
· blocks 6
#27
batchCancelOrders
#31
setData
#32
0x36326531
#36
0xc7e3ec2c
#2
0x0c7abd22
· blocks 5
#3
0x575c0012
· blocks 1
#24
0x98717539
· blocks 5
#8
0x719d975a
· blocks 3
#10
execute
· blocks 1
#25
0x5a5d9a99
· blocks 1
#28
0x0c7abd22
#33
execOrders
· blocks 2
#11
execute
#15
0xab083028
· blocks 2
#26
0x98717539
· blocks 1
#34
execOrders
· blocks 1
#16
0xab083028
· blocks 1
#29
execFwdPositionOps
· blocks 1
#35
execOrders
#17
0xab083028
#30
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
8
w2
10
w2
11
w3
13
w0
15
w3
16
w4
17
w5
23
w0
24
w1
25
w2
28
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xa02e5cdd…76b8
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x126a0344…4465
0x34b655…2a6f
6 touches
3 conflicts
0x45866eab…abfa
0x34b655…2a6f
6 touches
3 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:
Kuru Exchange: MarginAccount
15 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity