pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,485,403
← previous block
next block →
recent activity
Analyzing
Block #99,485,403
38 transactions · 32 stateful · 2026-08-27 01:36:15 UTC
Parallelism
87
/100
Blocked
44
%
Avg conflicts / tx
0.68
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,485,403
· 38 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0xa96df62f
#4
0x6a8f9507
· blocks 1
#5
execute
#6
execute
#7
0xab083028
· blocks 1
#9
0x5acec890
· blocks 1
#10
0x5acec890
#11
0x5acec890
#12
execOrders
· blocks 3
#14
0x59558d29
· blocks 1
#16
execPerpOps
#17
execPerpOps
#18
updateDataFeedsValuesPartial
#21
0x3f5c179b
#22
0x3f5c179b
#27
0x6a8f9507
#28
setData
#29
setData
#30
0x555ce2…d096
#31
execOrders
#32
execOrders
· blocks 4
#33
execOrders
#2
0x0c7abd22
· blocks 3
#13
execOrder
· blocks 1
#15
0x59558d29
#19
execFwdPositionOpsV2
#25
0xed82b078
#26
0x6a8f9507
#34
execOrders
· blocks 3
#8
0x5acec890
#20
execFwdPositionOpsV2
· blocks 2
#35
execOrders
· blocks 2
#23
execFwdPositionOpsV2
· blocks 1
#36
execOrders
· blocks 1
#24
redeemDelegations
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
7
w0
8
w2
9
w0
12
w0
13
w1
14
w0
15
w1
19
w1
20
w2
23
w3
24
w4
25
w1
26
w1
32
w0
34
w1
35
w2
36
w3
37
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00500a94…20d5
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0xb1856468…e84f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb1
0x1b6862…e19c
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
10 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity