pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,615,444
← previous block
next block →
recent activity
Analyzing
Block #83,615,444
26 transactions · 19 stateful · 2026-06-25 14:09:02 UTC
Parallelism
65
/100
Blocked
53
%
Avg conflicts / tx
1.04
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,615,444
· 26 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x50a0b275
#2
0x6a3d36f6
· blocks 1
#4
0xed82b078
#5
0xab083028
#6
0xab083028
#7
0xab083028
#8
updateDataFeedsValuesPartial
#9
0x5a5d9a99
· blocks 6
#15
0x6a3d36f6
#16
setData
#19
0x6a3d36f6
#20
0xe9316489
#21
0xd78a92…f032
#24
0xc7e3ec2c
#25
0xc7e3ec2c
#3
0x6a3d36f6
#10
0x5a5d9a99
· blocks 6
#11
0x5a5d9a99
· blocks 5
#12
0x98717539
· blocks 3
#13
0x98717539
· blocks 2
#14
0x98717539
· blocks 1
#17
execFwdPositionOps
· blocks 2
#18
execFwdPositionOps
#22
execOrders
· blocks 1
#23
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
9
w0
10
w1
11
w2
12
w3
13
w4
14
w5
17
w6
18
w7
22
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
8 touches
6 conflicts
0x75cdffd8…c217
0x34b655…2a6f
8 touches
6 conflicts
0x2484cc15…5afc
0x34b655…2a6f
6 touches
3 conflicts
0x5941ac48…c525
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x1c4e152b…b9f1
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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:
Perpl
15 conflicts on slot
0xe99d8e683a…2ea16e
Audit this contract →
← previous block
·
next block →
recent activity